(fix: #2884) iOS NFC: Ensure that Session is closed when an error causes it to become invalid #2885
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed
Original issue: #2884
Essentially, there are some cases where an NFC session becomes invalid, but the plugin doesn't properly close the session. This can occur if the user cancels the session before writing to a card, for example. In these cases, any subsequent writes fail immediately because a session is open, but it is invalid.
Changes made
In the case that a session is invalidated, instead of just logging the error and rejecting the invoke call, the session is also invalidated now.